Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1118

reference: 513-tree-1
name: 1118
tree-preservation-order: undefined
513-tpo-1
uprn
address-text
point: POINT (-1.021563 50.898630)
geometry: MULTIPOLYGON (((-1.021506 50.898624,-1.021509 50.898636,-1.021517 50.898646,-1.021529 50.898654,-1.021545 50.898659,-1.021562 50.898661,-1.021580 50.898659,-1.021596 50.898654,-1.021609 50.898646,-1.021617 50.898636,-1.021620 50.898625,-1.021617 50.898614,-1.021609 50.898604,-1.021597 50.898596,-1.021581 50.898591,-1.021564 50.898589,-1.021546 50.898591,-1.021530 50.898596,-1.021517 50.898603,-1.021509 50.898613,-1.021506 50.898624)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL